====== SEFI Analysis ======

Plots of SU, POR and GSIG SEFIs found in the configmon logs with Weibull parameters\\

{{ ::data_analysis:v7-dynamic:201703-tamu:SEFI_Cross_Section_Plots.pdf |}} \\

Zip archive with SEFI counter values\\

{{ ::data_analysis:v7-dynamic:201703-tamu:SEFI_files.zip |}} \\

Files within this archived are named starting with the run number followed by the SEFI type.
Each file is comma delimited. The first number of each line is the line number in the original configmon where the data can be found. This is followed by a date/time stamp. Last is the counter value. For example the contents of "0031 POR SEFIs.txt" are as follows:\\

1, 3/10/2017 5:27:27 AM,  0\\
3076, 3/10/2017 5:28:15 AM,  1\\
6384, 3/10/2017 5:29:07 AM,  10241\\
6385, 3/10/2017 5:29:07 AM,  1\\
9161, 3/10/2017 5:29:51 AM,  2\\
10203, 3/10/2017 5:30:07 AM,  3\\
13282, 3/10/2017 5:30:55 AM,  4\\

The first line is the first recorded value in the configmon log for run 31. The number of POR SEFIs at this time was 0 as expected when logging starts. The next line shows the first POR SEFI occurred at line number 3076 in the configmon log for run 31 and so on. For data plotting and cross sections shown in the PDF file, large values such like 10241 shown above were reduced modulo 512. So, this becomes 1 and the POR SEFI count for run 31 was taken to be 4.

Runs with no recorded SEFIs of have been omitted with the possible exception of runs 81 and 91. For both runs 81 and 91 there are two separate configmon logs. This ambiguity in the log files was not resolved.